Problem Note 58770: Hadoop Distributed File System (HDFS) table names are not created correctly when the name contains uppercase letters or spaces
Error messages like the following might be generated when you write to the Hadoop Distributed File System (HDFS) with a LIBNAME statement:
ERROR: Compilation error.
ERROR: Base table or view not found <name specified in code>
ERROR: Table "<name specified in code>" does not exist or cannot be accessed
This problem is most likely to occur if you include spaces or uppercase letters when specifying the connection options HDFS_DATADIR='path' and HDFS_METADIR='path'.
The sample code on the Full Code tab illustrates both the incorrect and correct way to specify these options.
To circumvent the problem, do not include spaces or uppercase letters in the path that is specified with the HDFS_DATADIR='path' and HDFS_METADIR='path' connection options.
Uppercased letters within path names are supported in SAS® 9.4M4, and spaces within path names are supported in SAS® 9.4M6.
Operating System and Release Information
SAS System | SAS/ACCESS Interface to Hadoop | Microsoft® Windows® for x64 | 9.4 TS1M3 | 9.4 TS1M4 |
Microsoft Windows 8 Enterprise 32-bit | 9.4 TS1M3 | 9.4 TS1M4 |
Microsoft Windows 8 Enterprise x64 | 9.4 TS1M3 | 9.4 TS1M4 |
Microsoft Windows 8 Pro 32-bit | 9.4 TS1M3 | 9.4 TS1M4 |
Microsoft Windows 8 Pro x64 | 9.4 TS1M3 | 9.4 TS1M4 |
Microsoft Windows 8.1 Enterprise 32-bit | 9.4 TS1M3 | 9.4 TS1M4 |
Microsoft Windows 8.1 Enterprise x64 | 9.4 TS1M3 | 9.4 TS1M4 |
Microsoft Windows 8.1 Pro 32-bit | 9.4 TS1M3 | 9.4 TS1M4 |
Microsoft Windows 8.1 Pro x64 | 9.4 TS1M3 | 9.4 TS1M4 |
Microsoft Windows 10 | 9.4 TS1M3 | 9.4 TS1M4 |
Microsoft Windows Server 2008 | 9.4 TS1M3 | 9.4 TS1M4 |
Microsoft Windows Server 2008 R2 | 9.4 TS1M3 | 9.4 TS1M4 |
Microsoft Windows Server 2008 for x64 | 9.4 TS1M3 | 9.4 TS1M4 |
Microsoft Windows Server 2012 Datacenter | 9.4 TS1M3 | 9.4 TS1M4 |
Microsoft Windows Server 2012 R2 Datacenter | 9.4 TS1M3 | 9.4 TS1M4 |
Microsoft Windows Server 2012 R2 Std | 9.4 TS1M3 | 9.4 TS1M4 |
Microsoft Windows Server 2012 Std | 9.4 TS1M3 | 9.4 TS1M4 |
Windows 7 Enterprise 32 bit | 9.4 TS1M3 | 9.4 TS1M4 |
Windows 7 Enterprise x64 | 9.4 TS1M3 | 9.4 TS1M4 |
Windows 7 Home Premium 32 bit | 9.4 TS1M3 | 9.4 TS1M4 |
Windows 7 Home Premium x64 | 9.4 TS1M3 | 9.4 TS1M4 |
Windows 7 Professional 32 bit | 9.4 TS1M3 | 9.4 TS1M4 |
Windows 7 Professional x64 | 9.4 TS1M3 | 9.4 TS1M4 |
Windows 7 Ultimate 32 bit | 9.4 TS1M3 | 9.4 TS1M4 |
Windows 7 Ultimate x64 | 9.4 TS1M3 | 9.4 TS1M4 |
64-bit Enabled AIX | 9.4 TS1M3 | 9.4 TS1M4 |
64-bit Enabled Solaris | 9.4 TS1M3 | 9.4 TS1M4 |
HP-UX IPF | 9.4 TS1M3 | 9.4 TS1M4 |
Linux for x64 | 9.4 TS1M3 | 9.4 TS1M4 |
Solaris for x64 | 9.4 TS1M3 | 9.4 TS1M4 |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
When you write to the HDFS, it is important not to use spaces or uppercase letters in the HDFS_DATADIR='path' or HDFS_METADIR='path' connection options. The sample code below illustrates this.
/* These are incorrectly written with spaces and uppercase letters */
libname hdfs hadoop server='abc009.unx.xxx.com'
HDFS_DATADIR='/user/myid/X Logs'
HDFS_METADIR='/user/myid/X Logs/metadata';
/* This is the correct way to specify the connection options */
libname hdfs hadoop server='abc009.unx.xxx.com'
HDFS_DATADIR='/user/myid/xlogs'
HDFS_METADIR='/user/myid/xlogs/metadata';
Type: | Problem Note |
Priority: | high |
Topic: | Data Management ==> Access ==> Client/Server
|
Date Modified: | 2018-11-13 10:55:08 |
Date Created: | 2016-08-11 11:17:59 |